What is advantage and disadvantage between Static RPC Ports and RPC Ports on a Client Access Server 2010 ? Thank You

Normal RPC behavior is for the client and the server to communicate over the RPC Port Mapper (Port 135) and negotiate what ports they will use for the application from a range of available ports. This prevents conflicts in port usage between applications. The disadvantage is that it complicates load balancer and firewall configuration, because you cannot predict which port the application will use. Static port assignment locks the application down to a specific port or ports. The disadvantage of this is that it introduces the possibility of conflict with other applications that may have specified those same ports. The advantage is that it makes load balancing and firewall configuration easier because now you know which ports will be used. [string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

I would also add that one disadvantage in setting static ports is the way those ports are set may change with service packs and version migrations that could complicate upgrades.

I would also add that one disadvantage in setting static ports is the way those ports are set may change with service packs and version migrations that could complicate upgrades.

On Sat, 18 Aug 2012 13:59:19 +0000, A_D_ wrote: >I would also add that one disadvantage in setting static ports is the way those ports are set may change with service packs and version migrations that could complicate upgrades. There's something to be said for the Unix SysV (and Linux or BSD) method starting "services". The admin gets to control what starts and in what order they start. Windows is a crapshoot. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Sat, 18 Aug 2012 13:59:19 +0000, A_D_ wrote: >I would also add that one disadvantage in setting static ports is the way those ports are set may change with service packs and version migrations that could complicate upgrades. There's something to be said for the Unix SysV (and Linux or BSD) method starting "services". The admin gets to control what starts and in what order they start. Windows is a crapshoot. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP